Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[5.3] Let worker ungracefully exit on memoryExceeded #17296

Conversation

lifeofguenter
Copy link
Contributor

This allows us to distinguish between a graceful exit (shouldRestart) and application crashes (memoryExceeded) that should trigger an autorestart according to supervisord.

@lifeofguenter lifeofguenter force-pushed the stop-worker-ungracefully-on-memory-leak-53 branch from 16a0d7d to 7e10d2d Compare January 12, 2017 12:33
@lifeofguenter lifeofguenter force-pushed the stop-worker-ungracefully-on-memory-leak-53 branch from 7e10d2d to 9ba89c7 Compare January 12, 2017 12:52
@taylorotwell
Copy link
Member

Please send to 5.4 branch.

@GrahamCampbell GrahamCampbell changed the title Let worker ungracefully exit on memoryExceeded [5.3] Let worker ungracefully exit on memoryExceeded Jan 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants